Changes are coming to https://stigviewer.com.
Take our survey to help us understand your usage and how we can better serve you in the future.
Take Survey
The system must be checked weekly for unauthorized setuid files as well as unauthorized modification to authorized setuid files.
Overview
| Finding ID | Version | Rule ID | IA Controls | Severity |
|---|---|---|---|---|
| V-803 | GEN002400 | SV-37592r2_rule | DCSL-1 | Medium |
| Description |
|---|
| Files with the setuid bit set will allow anyone running these files to be temporarily assigned the UID of the file. While many system files depend on these attributes for proper operation, security problems can result if setuid is assigned to programs allowing reading and writing of files, or shell escapes. |
| STIG | Date |
|---|---|
| Red Hat Enterprise Linux 5 Security Technical Implementation Guide | 2013-01-17 |
Details
| Check Text ( C-36666r3_chk ) |
|---|
| Ask the SA for the weekly automated or manual process used to generate a list of setuid files on the system and compare it with the prior list. If no such process is in place, this is a finding. Review the process. If the process does not identify and report changes in setuid files, this is a finding. NOTE: For MAC I systems, increase the frequency to daily. |
| Fix Text (F-31627r2_fix) |
|---|
| Establish a weekly automated or manual process to generate a list of suid files on the system and compare it with the prior list. To create a list of suid files: # find / -perm -4000 > suid-file-list NOTE: For MAC I systems, increase the frequency to daily. |